[Monitor] adding metricalerts api specifications#2316
[Monitor] adding metricalerts api specifications#2316LeoVannelli wants to merge 7 commits intoAzure:masterfrom
Conversation
|
@LeoVannelli @ravbhatnagar has this gone through the API review board? |
|
No, that is what I am hopefully submitting for.
|
|
@LeoVannelli you're at the right place, just wanted to confirm 🙂 |
|
This commit was treated and no generation was made for Azure/azure-sdk-for-go |
|
This commit was treated and no generation was made for Azure/azure-sdk-for-python |
|
This commit was treated and no generation was made for Azure/azure-sdk-for-python |
|
This commit was treated and no generation was made for Azure/azure-sdk-for-go |
|
This commit was treated and no generation was made for Azure/azure-sdk-for-python |
| }, | ||
| "default": { | ||
| "description": "BadRequest", | ||
| "schema": { "$ref": "#/definitions/CloudError" } |
There was a problem hiding this comment.
Make sure this name is the same we use in the other specs. So that our customers know what type will be returned in an error and we do not need to change PowerShell later.
There was a problem hiding this comment.
@LeoVannelli if the type is defined in another spec, I'd actually recommend referencing it directly (see here for example syntax).
Automation for azure-sdk-for-goEncountered a Subprocess error: (azure-sdk-for-go)
Command: profileBuilder -s list -l ./profiles/2017-03-09/defintion.txt -name 2017-03-09 Error: unknown command "2017-03-09" for "profileBuilder"
Run 'profileBuilder --help' for usage.
unknown command "2017-03-09" for "profileBuilder" |
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
Automation for azure-sdk-for-pythonA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
|
@LeoVannelli any updates regarding API review? |
|
@LeoVannelli did you see my email regarding the API review board process? Please schedule a meeting with azureapirbcore@microsoft.com (usually somewhere around Monday/Tuesday 2pm-4pm). |
Automation for azure-sdk-for-nodeNothing to generate for azure-sdk-for-node |
|
too old starting over |
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger